Greptile Summary

This PR refactors the commandline feature by extracting a createCommandlineController hook, inlining CommandlineInput, and switching to a named export — improving separation of concerns. However, the refactor introduces several behavioural regressions that leave the palette in broken states.

• toggle() only flips isOpen without calling resetSearch() or setScope(\"root\"), so Ctrl+K-to-close leaves a dirty query and scope that re-appear on the next open.
• The global keydown handler is now always active (not guarded by isOpen), causing Escape and Backspace to have unintended side-effects when the palette is closed.
• The CommandlineInput is missing bg-transparent and text-(--text), which can produce a white input background that clashes with the dark panel on some browsers.

Confidence Score: 2/5

The commandline palette has multiple regressions — stale state on keyboard close, always-on key listeners with unintended effects, missing theme reset on backdrop close, and lost input styling — that together make the feature unreliable.

The core close path via toggle() (Ctrl+K) leaves query and scope dirty, causing the palette to reopen in a wrong state. Combined with the always-active Escape listener and the theme-reset gap noted in earlier threads, the refactored controller introduces more breakage than the original on the main interaction paths.

apps/frontend/src/features/commandline/components/commandline.tsx needs careful attention — both the toggle() close path and the global keydown handler logic.

_{Reviews (3): Last reviewed commit: "revert keybind" | Re-trigger Greptile}

Want your agent to iterate on Greptile's feedback? Try greploops.